For projects, there are stakeholders, schedule constraints and funding availability that will affect which development approach you would use. We will be looking at each of these and what criteria you should consider when looking at the development approach to take. All lessons are based on the PMBOK®, 6th and 7th Edition.
CAPMP, PMP and PMBOK are registered marks of Project Management Institute, Inc.
Sign up for the new Interactive PMP!
Get ready to ace the PMP exam like never before with Interactive PMP! Our interactive course is a game-changer, combining fun games and bite-sized videos to help you conquer the PMP certification. From project planning to risk management, we've got you covered. Feel the excitement as you master complex concepts effortlessly, thanks to our engaging and interactive approach. No more boring textbooks or sleep-inducing lectures. With the Interactive PMP, you'll be on your way to PMP success in no time! Don't wait, grab this opportunity to turbocharge your career.
Sign up to get updates on new episode
Email us: info@pmnotebooks.com
PMNotebooks.com
Facebook | Instagram | Twitter | LinkedIn | YouTube
About Kaye B
Medium | LinkedIn
For projects, there are stakeholders, schedule constraints and funding availability that will affect which development approach you would use. Again, there is predictive, adaptive and hybrid approaches. We’ll be discussing what criteria to consider before selecting the development approaches.
If your project requires a lot of stakeholder involvement, and we know how that goes, then you will need an adaptive method. Why? Because you will get one stakeholder that says to make the wall blue then their boss comes in and says make it grey. Digging back to one of the earlier podcasts, we talked about stakeholders and it’s advantageous to get your final direction from the stakeholder that has more power in the project. If you don’t have a lot of stakeholders to consider or the workflow of the stakeholders are pretty set, then you can possibly use predictive.
Another one is schedule constrains. If there is a need, or rush, to deliver a piece of the project but you are not 100% ready, then an adaptive approach is beneficial. But if your service, product or result doesn’t have an immediate need or you’ve done it before so the timeline is pretty straightforward, then predictive would work.
If funding is uncertain then an adaptive approach is best. Things like minimum viable products are usually adaptive in nature because it takes less investment than an elaborate product which makes using the adaptive approach better. On the opposite end, if you know you are getting funding for the project, predictive may work.
For organizations, variables such as the structure, culture, capability, project team size and location can affect the development approach that you would use. Let’s get some details.
An organizational structure that has many levels, a rigid reporting structure and a bureaucracy most likely uses a predictive approach. Why, the higher level people want to know what’s going on and most likely have less appetite for work that is done in iterations.
If you are in a company culture where they thrive on project team self-management, then adaptive approach works better. If the organization likes the work to be planned out and progress is measured against baselines, the predictive approach fits better.
If your organization has a good mindset of change, especially at the executive level, then you have more flexibility on using different approaches and are most likely to use adaptive development because they don’t mind the change.
Project team size and location. This may spark a bit of debate but remember that this is according to the PMBOK, not your personal belief. Always think about that when you are studying for the PMP but I digress. Adaptive approaches tend to work better with teams that are located in the same physical space and the team is small. Larger teams and teams that are mostly virtual do better by using a predictive approach
We talked about this from an organization perspective but know that teams and departments can use different approached. Your executive c-level team may use predictive approach to say plan for the next quarterly earnings meeting but the engineering team uses an adapative approach when creating the new app. Look at your project and organization when deciding which development approach works for you and your team.
That is your PMP in a Snap. We’ll see you again next week.